Configuration management for models : generic methods for model comparison and model co-evolution

p a r e n t O p e r a t i o n + n a m e : S t r i n g + v i s i b i l i t y : V i s i b i l i t y K i n d + i s C o n s t r u c t o r : B o o l e a n o p e r a t i o n s P a r a m e t e r + n a m e : S t r i n g + p o s i t i o n I n d e x : I n t e g e r * * A d d e d O p e r a t i o n D e l e t e d O p e r a t i o n C h a n g e d O p e r a t i o n A d d e d P a r a m e t e r D e l e t e d P a r a m e t e r C h a n g e d P a r a m e t e r u p d a t e d E l e m e n t u p d a t e d E l e m e n t u p d a t e d E l e m e n t u p d a t e d E l e m e n t Figure 1.8: State-based model differences metamodel for UML models elements model added, deleted, or changed element instances between two compared models. An example metamodel for the description of operation-based model differences between Ecore based models, defined in [70], is depicted in Figure 1.9. Notice that unlike in the state-based differences metamodel, the focus of the operation-based metamodel are model operations. In particular there are create and delete operations, which model adding or deleting complete model elements, and there are feature operations, which model the change to model elements (because in Ecore features represent attributes of model elements, or relations between model elements). Both described approaches have deficiencies, which will be discussed in Chapter 3. Moreover, in Chapter 3, we describe our approach to the representation of state-based model differences, that solves some deficiencies of the existing representations of state-based model differences.